Skip to content

Fix ClusterApiToken not persisted on secondary after initJoin#1851

Closed
comerford wants to merge 1 commit intoTechnitiumSoftware:masterfrom
comerford:fix/cluster-api-token-not-synced
Closed

Fix ClusterApiToken not persisted on secondary after initJoin#1851
comerford wants to merge 1 commit intoTechnitiumSoftware:masterfrom
comerford:fix/cluster-api-token-not-synced

Conversation

@comerford
Copy link
Copy Markdown

@comerford comerford commented Apr 26, 2026

See: #1848

  • initJoin calls SyncConfigFromAsync → RestoreConfigAsync(isConfigTransfer: true)
  • The isConfigTransfer branch filters sessions to only ApiToken, dropping ClusterApiToken
  • Token lives in memory after join but is never written to auth.config on the secondary
  • On service restart, ClusterManager can't find the token so you get "No API token was found for the Cluster domain"

This is a simple fix to add the ClusterAPI token so it won't get filtered.

@comerford comerford mentioned this pull request Apr 26, 2026
Closed
@ShreyasZare
Copy link
Copy Markdown
Member

ShreyasZare commented Apr 26, 2026

Thanks for the PR. Have fixed this bug with v15.0.1 release.

@comerford comerford deleted the fix/cluster-api-token-not-synced branch April 26, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@comerford @ShreyasZare